Hello Everyone, I have few questions about the proper steps to deploy the SSIS 2008 package with config files on to the dev server. I created the packages and XML config files. I have stored the config files locally on my computer in the directory : "C:\Documents and Settings\User1\My Documents\configfile". I plan to create a manisfest file, and copy the deployment folder on to the dev server. I want to know on the Dev server where should I copy the deployment folder? Also, where should I store the xml config files on the dev server as I do not find the same path as on my local desktop. So, can I place the config files in any folder on the Dev Server? Thanks a lot.

Create on DEV and Prod the same folder for ex. "C:\PackageConfiguration" and store the config there. The path to config file is fix, there is no chance to give a relative path or change the path without opening the SSIS-Packages on Prod. with BIDS.

1) Before the deployment to prodcution, you could change the SSIS configuration to use environment variable which can store the path to the configuration files. 2) While dpeloyment to the production , create the same environment varaible exactly which is available in the packages. 3)This way, you could just change the path in the environment variable and this gets reflected in the packages. 4) For the deployment manifest, it can be copied to any path and it will deploy whether to file or sql server system.Please mark my post as an answer if I helped you to resolve the issue or vote up if I helped you.Thanks. Regards and good Wishes, Deepak.

Hi All, Thanks a lot for your replies. The config file part is the one which is confusing me, please help me with it. Is there any way to acheive this without creating a environment variable? This is because I am not sure if everyone agrees on creating an environment variable. On the other hand suppose I create a same folder(C:\packageconfig) as on my local computer on the dev server. But I am unable to do so as the directory path on the dev server starts with "\\servername\ssis$\..." Please let me know if I am understanding it correctly.

No, you hav to create a local path on DEV and Prod. Environment variable is nice if the Admins will allow it but unfortunatly they don't in the most cases.

Thanks a lot, ok so here is my understanding. You mean if on my local desktop I create a directory as "C:\SSIS\Package\configurations" to store the XML config files, then on the Devlopment server also I should create the exact same directory and copy the config files there before deployment? For creating the same directory on the dev server, I think i should ask to DBA to do it as I do not have permissions. What happens if I do not create a same directory and just install it in the "package installation folder" when deploying which is defaulted to "C:\Program Files\Microsoft SQL Server\100\DTS\Packages\<Project Folder>"?

Hi Christa, I have a question about the config file location. I did deploy the packages with the config files successfully on the dev server. But I did not create a same path on dev server as my local desktop to store the xml config files. Instead, when I copied the deployment folder on to the target server (dev server), I ran the manifest file for file based deployment and it prompted for the location to store the package and its dependencies (config files etc.). I did provide a new location to store them and when I completed the deployment I executed the package using SSMS and it ran successfully and picked up the config file from the new location on the dev server. So, my understanding is that we can provide a new location for the xml config file on the server (dev or prod) when using the manifest file for deployment? But if we manully import the package on to the integration services server(dev or prod), we need to place the config file in the exact location used for creating the file on the local desktop?

There is now an utility available in CodePlex which can be used to batch update SSIS Package Configuration File paths without using BIDS: http://ssisconfigeditor.codeplex.com/